Skip to content

docs: rewrite CONTRIBUTING to reflect published, active project#28

Open
dmchaledev wants to merge 1 commit into
mainfrom
claude/magical-ptolemy-i0uo2f
Open

docs: rewrite CONTRIBUTING to reflect published, active project#28
dmchaledev wants to merge 1 commit into
mainfrom
claude/magical-ptolemy-i0uo2f

Conversation

@dmchaledev

Copy link
Copy Markdown
Contributor

Summary

CONTRIBUTING.md currently turns away the very contributions this project is soliciting. It states the package is "in incubation", "not yet open for external contributions", and asks readers to "check back after the package is published to npm."

All three claims are inaccurate:

The result is a contributor guide whose only message is "go away, come back later" — a direct conversion-killer for an open-source security tool that, per the README, is "Part of the HailBytes open-source security toolkit."

Change

Replace the stale notice with an accurate, useful contributor guide:

  • How to report bugs / propose features
  • Dev setup (clone + npm install, Node >=18 per engines)
  • A table of the real npm scripts (test, test:watch, test:coverage, lint, typecheck, build, cli)
  • The exact checks CI runs on PRs to main (lint + test + build)
  • Conventional Commits guidance matching the existing history (e.g. fix(cli): ..., feat(diff): ..., docs: ...)
  • Standard PR guidelines and the MIT license note

Why this is high-leverage and low-risk

  • Fixes a concrete, verifiable defect (factually wrong, self-contradicting docs) rather than adding speculative content.
  • Conflict-free with everything in flight — all open PRs/issues touch src/ or the release workflows; this only touches CONTRIBUTING.md.
  • Docs-only, no behavior change.

🤖 Generated with Claude Code


Generated by Claude Code

CONTRIBUTING.md stated the package was "in incubation", "not yet open
for external contributions", and asked readers to "check back after the
package is published to npm". All three are inaccurate: @hailbytes/sbom-diff
is published on npm (v1.0.1 is the latest dist-tag) and is actively taking
contributions (multiple PRs merged; many open).

The stale notice actively discouraged the contributions the project is
soliciting. Replace it with an accurate contributor guide: dev setup, the
real npm scripts (test/lint/typecheck/build), the CI checks, Conventional
Commit style matching the existing history, and PR guidelines.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015FXrgnfVQVMvwjMtsaZqvL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants